Skip to content

[8.0] fix: do not reset files for not yet submitted jobs - #8583

Open
atsareg wants to merge 1 commit into
DIRACGrid:rel-v8r0from
atsareg:fix-monitor-files
Open

[8.0] fix: do not reset files for not yet submitted jobs#8583
atsareg wants to merge 1 commit into
DIRACGrid:rel-v8r0from
atsareg:fix-monitor-files

Conversation

@atsareg

@atsareg atsareg commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

The removed operation was reseting files to Unused for tasks that were created but job not yet submitted. As a result new jobs were created for the same files multiple files.

A fix was needed in the pre-commit configuration for the flynt part as by default it uses python3.14 version not compatible with 3.11. I think this should be harmless

BEGINRELEASENOTES

*Transformation
FIX: WorkflowTasks - do not reset files for not yet submitted jobs

ENDRELEASENOTES

@fstagni

fstagni commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Looking at this PR, I realize that there is the "same" function in https://github.com/DIRACGrid/DIRAC/blob/rel-v8r0/src/DIRAC/TransformationSystem/Client/RequestTasks.py#L366

which is certainly working fine (in the context of replication transformations, but still...). Can you compare the 2 and check their differences?

@atsareg
atsareg requested review from aldbr and fstagni June 12, 2026 21:07
@atsareg

atsareg commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Yes, this is a good confirmation of this PR. In the replication transformations the files are ONLY checked for tasks that were created and got the ExternalID:

# Only consider tasks that are submitted, ExternalID is a string
.

Here, there should be the same logic: files are reserved while the jobs are not yet submitted, those should not be reset to UNUSED because it is just a slow job submission in an overloaded system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants